Please address the comments from this code review:

## Individual Comments

### Comment 1
<location path="module/server/app.py" line_range="24-33" />
<code_context>
 from starlette.staticfiles import StaticFiles


+class ASCIIJSONResponse(JSONResponse):
+    """Serialize non-ASCII characters as ``\\uXXXX`` for proxy compatibility."""
+
+    def render(self, content) -> bytes:
+        return json.dumps(
+            content,
+            ensure_ascii=True,
+            allow_nan=False,
+            indent=None,
+            separators=(",", ":"),
+        ).encode("utf-8")
+
+
</code_context>
<issue_to_address>
**suggestion:** Consider reusing JSONResponse’s encoding pipeline rather than hard-coding json.dumps here.

Overriding `render` with a direct `json.dumps` call bypasses JSONResponse’s encoding pipeline (e.g., `jsonable_encoder`, app-level custom `dumps`, future switches to `orjson`). To keep this response consistent with the rest of the framework, consider delegating to `super().render` and only adjusting the necessary parameters (such as `ensure_ascii`), or overriding the relevant hook used by JSONResponse for dumps instead of reimplementing the full render logic.

Suggested implementation:

```python
from pathlib import Path
import json

from contextlib import asynccontextmanager

from starlette.staticfiles import StaticFiles
from fastapi.responses import JSONResponse
from fastapi.encoders import jsonable_encoder


class ASCIIJSONResponse(JSONResponse):
    """Serialize non-ASCII characters as ``\\uXXXX`` for proxy compatibility."""

    def render(self, content) -> bytes:
        # Reuse FastAPI's JSON encoding pipeline (jsonable_encoder, etc.)
        encoded_content = jsonable_encoder(content)
        return json.dumps(
            encoded_content,
            ensure_ascii=True,
            allow_nan=False,
            indent=None,
            separators=(",", ":"),
        ).encode("utf-8")

```

1. If your project already imports `JSONResponse` and/or `jsonable_encoder` elsewhere in this file, adjust the import section to avoid duplicates and keep a consistent import style.
2. If you use a custom JSON dumps function (e.g. via app-level configuration or `ORJSONResponse`), and you want `ASCIIJSONResponse` to participate in that configuration, consider:
   - Accepting a `json_dumps` callable in `__init__` (defaulting to the app's configured dumps), and
   - Using that callable instead of the standard `json.dumps` inside `render`, while still passing `ensure_ascii=True` via keyword arguments if the callable supports it.
</issue_to_address>